home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Library
/
RoseWare - Network Support Library.iso
/
btrieve
/
xtros2.exe
/
XTROS2.DOC
< prev
next >
Wrap
Text File
|
1993-12-14
|
39KB
|
1,113 lines
NOVELL TECHNICAL INFORMATION DOCUMENT
DOCUMENT PROCESSING INFO: NOVLIB LIB7
TITLE: Xtrieve OS/2 v4.11 patch E
DOCUMENT ID:
DOCUMENT REVISION: A
DATE: 13DEC93
AUTHOR: MGAINES
ALERT STATUS: Yellow
DISTRIBUTION: Public
INFORMATION TYPE: Issue
README FOR: XTROS2.EXE
NOVELL PRODUCT CLASS: Database Products
NOVELL PRODUCT and VERSION: Xtrieve PLUS 4.1x
CATEGORY: OS/2
ABSTRACT: XTROS2.EXE contains the OS/2 environment patch release E for Xtrieve PLUS v4.11 programs and utilities.
================================================================================
Disclaimer and Copyright
========================
Novell(R), Inc. makes no representations or warranties with respect to the
contents or use of this document, and specifically disclaims any express
or implied warranties of merchantability or fitness for any particular
purpose. Further, Novell, Inc. reserves the right to revise this document
and to make changes to its content, at any time, without obligation to
notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect
to any NetWare software, and specifically disclaims any express or implied
warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc. reserves the right to make changes to any and all
parts of NetWare software, at any time, without any obligation to notify
any person or entity of such changes.
PATCH.EXE is a proprietary product of PocketSoft. PATCH.EXE and Patch Build
generated files are distributed by Novell, Inc. under license from
PocketSoft.
Copyright (c) 1993 Novell, Inc. All rights reserved.
================================================================================
Contents
========
Installation Procedure
Patch File Information
Original File Information
Patch Set Descriptions
December 1992 Patches
April 1993 Patches
December 1993 Patches
Documentation Updates
December 1992 Updates
================================================================================
Installation Procedure
======================
The PATCHXTR.CMD and PATCH.EXE files discussed in this procedure require
OS/2 v1.1 or later.
The XTROS2.EXE file contains the following:
- This Readme document
- PATCH.EXE (a utility Novell provides for installing product patches)
- PATCHXTR.CMD (a batch file to facilitate patch installation)
- Xtrieve PLUS Patch files (XTRIEVE.411 and XQLCALLS.211)
- Replacement files (files with the same names as the files they replace)
To update Xtrieve PLUS v4.11, complete the following steps:
1. Create a directory on your system, and copy the XTROS2.EXE file to
that directory.
2. Use the utility PKUNZIP.EXE to unzip the zipped files.
3. Install the Xtrieve PLUS patch files (XTRIEVE.411 and XQLCALLS.211) as
follows:
a. Refer to the list of patch files in the section of this Readme file
entitled "Original File Information," find the original files on your
system, and ensure that your original files match those listed.
NOTE: This patch is cumulative; it contains all previous patches to
Xtrieve PLUS v4.11 for OS/2. Consequently, if you
installed a previous patch, you should restore the original
files by reinstalling them from the installation diskettes, or
by renaming the XTRIEVE.ORG file (created during the previous
patch installation) to XTRIEVE.EXE.
b. Use the DOS COPY command to copy the original files into the
directory that contains the unzipped patch files from XTROS2.EXE.
c. Run PATCHXTR, which verifies that you are patching the original
released version of the software, applies the patch, and gives the
original files an .ORG extension.
d. Use the DOS COPY command to copy the patched files back to the
original file's directory.
4. Install the replacement files as follows:
a. Find the directory that contains the original files to be replaced.
b. Before copying the replacement files, back up the original files
to a diskette or to another directory.
c. Use the COPY command to replace the original files with the
new files.
5. After applying the patches, you can remove the directory you created to
store the XTROS2.EXE file. You may also want to verify the version
numbers when you load each program. The version numbers should match
those listed in the next section, "Patch File Information."
================================================================================
Patch File Information
======================
Patch Set Filename: XTROS2.EXE
Date: 12-13-93
Files Included: XTROS2 DOC This document
XTROS2 TXT Short Readme
PATCH EXE 76981 1-30-92 5:00a
PATCHXTR CMD 3928 12-17-92 3:55p
Patch File: XTROS2 411 v4.11e 81578 12-08-93 12:08p
XQLCALLS 211 538 12-17-92 3:27p
Replacement Files: MAKE_XTA EXE v4.11c 74882 11-19-93 2:57p
XCFP EXE v4.11c 40946 11-19-93 2:53p
XHFP EXE v4.11b 26192 12-09-92 11:17a
XMENU EXE v4.11b 133592 12-09-92 11:14a
XTRIEVE MSG 39077 11-18-93 1:38p
XTRIEVE MEN v4.11c 13347 11-18-93 1:38p
================================================================================
Original File Information
=========================
To ensure you are patching the original files, compare the files to be
patched with those in the following list. This list shows the byte size
and the date and time stamps for the original release.
Patch these files:
XTRIEVE EXE v4.11 464362 8-13-92 11:21a
XQLCALLS ORG v2.11 399291 10-18-90 12:28p
Replace these files:
MAKE_XTA EXE v4.11 71738 6-25-92 7:45p
XCFP EXE v4.11 56994 6-25-92 8:07p
XHFP EXE v4.11 26192 6-25-92 8:06p
XMENU EXE v4.11 133592 9-16-92 12:57p
XTRIEVE MSG 39017 8-11-92 3:59p
XTRIEVE MEN v4.11 13347 8-11-92 3:59p
NOTE: You may have newer versions of the replacement files listed above
that you received in a previous patch release. Replace those
existing files with the files included in this current patch release.
================================================================================
Patch Set Descriptions
======================
This section describes each patch in the patch set. The patch descriptions
are grouped by release date. Within each release group, the patch
descriptions for the Xtrieve PLUS engine appear first, followed by those for
the utilities.
For each patch, the description includes one or more search strings. These
search strings indicate areas in which you may encounter the problem that the
patch addresses. The search strings may help you quickly determine whether
the patch you need for a specific problem is included in this patch set.
NOTE: In some cases, the text describes a problem or reported bug that the
update does NOT fix. In those cases, use the workaround provided.
* * * * * * * * *
December 1992 Patches
---------------------
The following information describes patches released in December 1992.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search String: DISPLAY ERRORS
Problem:
In the Report Layout screen, when you insert a field between two fields that
take up a relatively large portion of the screen, Xtrieve PLUS redraws the
screen incorrectly. This patch does not contain a fix; Xtrieve PLUS
accurately stores the new data.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: F8, HANG, MODIFYING, REPORT LAYOUT
Problem Fixed by This Patch:
When you repeatedly use the key sequence Shift+F8, F8, and Esc when modifying
or viewing groups or fields in a report layout, Xtrieve PLUS terminates.
This patch ensures that Xtrieve PLUS properly closes and reopens the report
layout windows, thus preventing Xtrieve PLUS from terminating.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: GROUP FIELD, GROUP SUMMARY, REPORT FIELD, REPORT SUMMARY
Problem Fixed by This Patch:
If you use a report field in a report field summary or a group field in a
group field summary, Xtrieve PLUS does not allow you to remove or modify the
field. This patch ensures that Xtrieve PLUS allows you to remove or modify
such fields.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: FORM/ADD EDIT SCREEN, INVALID RECORD
Problem Fixed by This Patch:
If you attempt to add an invalid record using the Form/Add edit screen,
Xtrieve PLUS exits the Form/Add edit screen and returns to the Form menu.
This patch ensures that if an error occurs when you attempt to add a record,
Xtrieve PLUS remains at the edit screen.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search String: REPORT LAYOUT
Problem Fixed by This Patch:
When XQL and Btrieve are loaded by Xtrieve PLUS, a report layout may become
corrupt in memory after you print the report. This patch ensures that
Xtrieve PLUS correctly maintains report layouts.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search String: REMOVE GROUP
Problem Fixed by This Patch:
If you remove a group from a report and then attempt to remove another
group, Xtrieve PLUS displays a repetitive list of groups from which to
choose. In addition, if you choose one of the listed groups, Xtrieve PLUS
causes the workstation to freeze. This patch ensures that Xtrieve PLUS
correctly displays lists of groups.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: BLANKS, IMPORT DATA, SDF
Problem Fixed by This Patch:
Xtrieve PLUS incorrectly imports data in Standard Data Format (SDF) if
blanks separate the data elements, as in the following example:
"Firstname", "Middlename", "Lastname"
This patch ensures that Xtrieve PLUS correctly imports SDF data.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: LVAR, NOTE, TRANSLATE, VARIABLE-LENGTH FIELDS
Problem Fixed by This Patch:
Xtrieve PLUS does not accurately perform view-to-view translations on
variable-length fields that are not of the same type. For example, you
cannot accurately translate a note field into an lvar field. This patch
ensures that Xtrieve PLUS correctly performs such translations.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: CREATE FILE, PAGE, PREALLOCATION
Problem Fixed by This Patch:
When you are creating files, Xtrieve PLUS allows you to preallocate no more
than 32,767 pages. This patch ensures that Xtrieve PLUS allows you to
preallocate up to 65,535 pages.
* * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: BTRIEVE, NEW COMMAND LINE OPTIONS, UNLOAD, XQL
Problem Fixed by This Patch:
Xtrieve PLUS does not unload Btrieve or XQL from memory if you loaded Btrieve
or XQL before you entered Xtrieve PLUS. If you do not have the utilities
BUTIL or NSUTIL, you cannot unload XQL or Btrieve from memory. This patch
makes available two new command line options you can specify when you load
Xtrieve PLUS:
/ua Unloads both XQL and Btrieve when you exit Xtrieve PLUS
/ux Unloads only XQL when you exit Xtrieve PLUS
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: CONDITIONAL, FIELD LIST, SCALAR FUNCTIONS,
USER-DEFINED FIELDS
Problem:
Xtrieve PLUS may not display all available fields in a field list when you
are defining a user-defined field that includes nested conditions or nested
scalar functions, as in the following example expression:
Result = SUBSTRING( SUBSTRING( SUBSTRING( Field3,5,20),2,Field2),5,Field1)
Workaround:
For each level of nesting, create a temporary, user-defined field, as in the
following example:
TempField1 = SUBSTRING( Field3,5,20)
TempField2 = SUBSTRING( TempField1,2,Field2)
TempField3 = SUBSTRING( TempField2,5,Field1)
Since Xtrieve PLUS embeds the temporary field definitions in the substring
field that references it, you can delete the interim temporary fields,
resulting in a single, user-defined field, as in the following example:
Result = TempField3
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: DECIMAL POINTS, INTEGER FIELDS, MASKS
Problem:
If you place a mask that contains decimal points (such as ZZZ,ZZ9.99) on an
integer field, you may get unexpected results in report summary fields. For
example, if the field's data is 38,470.00, the masked result is 384.70.
Workaround:
Masks on integer fields should not contain decimal points. Use a more
appropriate data type, such as decimal, float, money, or numeric.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.PDB
Search Strings: PRINTER, TABLOID SETTING
Problem:
The Tabloid setting of the XTRIEVE.PDB file specifies the Epson LQ-1500/2.0
printer instead of the IBM PC graphics printer.
Workaround:
Change the Tabloid setting as follows.
1. At a DOS workstation, enter SLATE XTRIEVE.PDB.
2. In the SLATE utility, follow these steps to set the Tabloid setting:
a. Select the Add/Edit Devices (Ptr Connections) option from the main
menu.
b. Select the 3001 Tabloid option from the Devices menu.
c. Use the Tab key to move to the Ptr Mfg field and press F9 to display
a list of printer manufacturers.
d. Select IBM.
e. Use the Tab key to move to the Ptr Type field and press F9 to display
a list of printer types.
f. Select PC Graphics Printer.
3. To exit SLATE, press F10 three times.
* * * * * * * * *
Product/Platform: OS/2 - MAKE_XTA.EXE, v4.11
Search Strings: 3, HANG, OPEN VIEWS
Problem Fixed by This Patch:
The MAKE_XTA utility hangs or returns Status Code 3 (File Not Open) when you
attempt to open certain views. This patch ensures that MAKE_XTA can open
such views.
* * * * * * * * *
Product/Platform: OS/2 - MAKE_XTA.EXE, v4.11
Search Strings: FIELD NAMES, LOWERCASE, UPPERCASE
Problem Fixed by This Patch:
The MAKE_XTA utility converts all letters in user-defined field names to
uppercase. This patch ensures that MAKE_XTA preserves lowercase letters in
field names.
* * * * * * * * *
Product/Platform: OS/2 - MAKE_XTA.EXE, v4.11
Search Strings: EQJOIN, EQUAL, JOIN, KEYWORD, NULL, NULLJOIN
Problem Fixed by This Patch:
The MAKE_XTA utility inserts incorrect keywords in .XTA files that contain
file joins. For example, MAKE_XTA uses the keyword EQUAL when it should use
the keyword EQJOIN. This patch ensures that MAKE_XTA inserts the correct
keywords.
* * * * * * * * *
Product/Platform: OS/2 - MAKE_XTA.EXE, v4.11
Search Strings: ADD KEYWORD, REPORT LAYOUT, SUM
Problem Fixed by This Patch:
If a report layout contains the calculation type SUM, the MAKE_XTA
utility inserts an extra .ADD. keyword in the XTA file. This patch ensures
that MAKE_XTA inserts the correct number of .ADD. keywords.
* * * * * * * * *
Product/Platform: OS/2 - MAKE_XTA.EXE, v4.11
Search Strings: ADJACENT FIELDS, BIT FIELDS
Problem Fixed by This Patch:
If a dictionary contains two or more adjacent fields of type bit, the
MAKE_XTA utility inserts only the first bit field in the .XTA file. This
patch ensures that MAKE_XTA inserts all bit fields.
* * * * * * * * *
Product/Platform: OS/2 - MAKE_XTA.EXE, v4.11
Search Strings: AUTOINC, INDEX ATTRIBUTES
Problem Fixed by This Patch:
The MAKE_XTA utility incorrectly extracts the index attributes of fields of
type autoinc. This patch ensures that MAKE_XTA retains index attributes as
defined in the original file.
* * * * * * * * *
Product/Platform: OS/2 - MAKE_XTA.EXE, v4.11
Search Strings: EXTRACT FILES, SUPPLEMENTAL INDEX
Problem Fixed by This Patch:
The MAKE_XTA utility fails when attempting to extract files that contain
supplemental indexes. This patch ensures that MAKE_XTA correctly extracts
supplemental indexes.
* * * * * * * * *
Product/Platform: OS/2 - MAKE_XTA.EXE, v4.11
Search String: DESCRIPTIVE FILENAME
Problem Fixed by This Patch:
If a descriptive filename is shorter than the actual filename, the MAKE_XTA
utility pads the rest of the descriptive filename with characters from the
actual filename. For example, given a descriptive filename of FILE and an
actual filename of TESTING, MAKE_XTA converts the descriptive filename to
FILEING. This patch ensures that MAKE_XTA inserts the correct descriptive
filename into the generated .XTA file.
* * * * * * * * *
Product/Platform: OS/2 - MAKE_XTA.EXE, v4.11
Search Strings: EXTRACT VIEWS, USER-DEFINED FIELDS
Problem Fixed by This Patch:
The MAKE_XTA utility incorrectly extracts files containing relatively large
user-defined fields. This patch ensures that MAKE_XTA correctly extracts
such files.
* * * * * * * * *
Product/Platform: OS/2 - MAKE_XTA.EXE, v4.11
Search Strings: CONDITIONAL USER-DEFINED FIELDS, MASKS
Problem:
If you define a conditional user-defined field in Xtrieve PLUS and you define
a mask for the field, MAKE_XTA does not maintain the mask when it creates the
.XTA file.
Workaround:
Edit the .XTA file to restore the mask definitions for each conditional
user-defined field you want masked.
* * * * * * * * *
Product/Platform: OS/2 - XCFP.EXE, v4.11
Search Strings: COMMANDS WITH NUMERALS, PAGE SIZE
Problem Fixed by This Patch:
The Xtrieve PLUS Command File Processor (XCFP) utility does not recognize the
command that specifies page size since the command begins with a numeral.
This patch ensures that XCFP recognizes commands that begin with numerals.
* * * * * * * * *
April 1993 Patches
------------------
The following information describes patches released in April 1993.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: MAXIMUM NUMBER OF VIEWS (819), MEMORY ERROR,
/V STARTUP OPTION
Problem Fixed by This Patch:
Xtrieve PLUS returns a memory error on View Release and/or Retain operations
when you specify more than 819 views. This patch ensures that when you
specify more than 819 views for the /V startup option (for example, /V:850),
you receive the following message:
Xtrieve: Invalid view parameter
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: INVALID COMMAND-LINE PARAMETER, TEMPORARY FILES,
XTRTMP_M.* FILE
Problem Fixed by This Patch:
When you supply Xtrieve PLUS with an invalid command-line parameter, the
program removes all temporary files except the XTRTMP_M.* file. This patch
ensures that Xtrieve PLUS correctly deletes all temporary files.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: BFLOAT DATA TYPE, RESTRICTION
Problem Fixed by This Patch:
Since Xtrieve PLUS v4.11b does not insert a bfloat data type correctly, any
restriction based on a bfloat data type returns invalid results. This patch
ensures that Xtrieve PLUS recognizes the version of the program that you are
using and correctly adapts the input value to work in that environment.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: EXITING XTRIEVE, SUSPENDED COMMAND FILE
Problem Fixed by This Patch:
When you use a CTRL+Break key sequence while an Xtrieve PLUS command file is
suspended, Xtrieve PLUS causes you to exit from the program. This patch
ensures that Xtrieve PLUS stops the command file execution rather than
exiting from the program.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: 2101, /D OPTION, DATA DICTIONARY, DICTIONARY SHOW, NSREQ
Problem Fixed by This Patch:
When you use the NetWare SQL Requester (NSREQ.EXE or NSREQS.EXE) to access
dictionaries through Xtrieve PLUS and the Dictionary Show command does
not display any dictionaries, restart the Requester and specify a larger
length for the data message with the /D option (Date Message Length). The
Show Dictionary command then displays a list of all available dictionaries.
This patch ensures that the NetWare SQL Requester displays Status Code 2101
(Data Message Buffer Is Too Small) when a request to read Xtrieve data, such
as a list of dictionaries, fails.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: 248, BLANKS, CHARACTER FIELD/LIST, INSERT
Problem Fixed by This Patch:
When you press Enter on a character field in an insert screen for which you
have defined a character list and no data is shown, Xtrieve PLUS returns
Status Code 248 (Invalid Size for Data Type) even if blanks are permitted in
that field. This patch ensures that Xtrieve PLUS handles such character
fields correctly.
* * * * * * * * *
Product/Platform: NetWare SQL - XTRIEVE.EXE, v4.11
Search Strings: GROUP/SUMMARY, REPORT LAYOUT, TRAP ERROR
Problem Fixed by This Patch:
When you choose Group/Summary in the Report Layout, Xtrieve PLUS receives a
trap error (the result of incorrectly initializing the Group/Summary
element), which may occur in all three environments (NetWare SQL, DOS, and
OS/2). This patch ensures that Xtrieve PLUS handles the Group/Summary
element correctly.
* * * * * * * * *
Product/Platform: OS/2 - MAKE_XTA.EXE, v4.11
Search Strings: BRACKETED CONDITIONAL FIELD, CONSTANT, USER-DEFINED FIELD
Problem Fixed by This Patch:
The MAKE_XTA utility does not properly convert constants when extracting a
view containing a user-defined field that includes a bracketed conditional
field. This patch ensures that MAKE_XTA handles such user-defined fields
correctly.
* * * * * * * * *
Product/Platform: OS/2 - MAKE_XTA.EXE, v4.11
Search Strings: COMMAND FILE, DEFINED VIEW, JUSTIFICATION, XCFP
Problem Fixed by This Patch:
When you use the MAKE_XTA utility to extract a defined view and then use the
Xtrieve Command File Processor (XCFP) to make that view into a command file,
Xtrieve drops the left/right/center justification. This patch ensure that
the MAKE_XTA utility places the correct justification information in the
.XTA file.
* * * * * * * * *
Product/Platform: OS/2 - MAKE_XTA.EXE, v4.11
Search Strings: FIELD, FLOATING POINT VALUES, MASKABLE DATA TYPE,
UNFORMATTING DATA
Problem Fixed by This Patch:
The MAKE_XTA utility is not handling maskable data type fields correctly,
causing an invalid mask when unformatting data. In addition, the utility
is not translating floating point values correctly. This patch ensures that
the MAKE_XTA utility handles both maskable data type fields and floating
point values correctly.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: HEWLETT PACKARD LASERJET PRINTER, VARIABLE-WIDTH FONTS
Additional Printer Information:
Variable-width fonts for the Hewlett Packard series of Laserjet printers do
not work correctly with Xtrieve PLUS.
* * * * * * * * *
December 1993 Patches
---------------------
The following information describes patches released in December 1993.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: GROUP, HANG, REMOVE, SUMMARIES
Problem Fixed by This Patch:
Xtrieve does not successfully remove a report group that contains a group
summary. This occurs when you use GROUP/REMOVE from the Report menu to
remove from a table a group containing other groups that themselves contain
group summaries. When you again choose GROUP/REMOVE, Xtrieve displays the
remaining group names multiple times in the list of groups. If you then try
to remove any of the remaining groups, the computer hangs. This patch
ensures that Xtrieve handles this type of operation correctly.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: HANG, PRINT, REPORT
Problem Fixed by This Patch:
When you attempt to print a report that contains groups, the printer
occasionally hangs after printing the first page. This problem occurs,
however, only when you position the groups so that subsequent groups print
on the same line as the first group. In that case, Xtrieve tracks the
current line and column positions inaccurately, attempts to place too much
information on a page, overwrites memory, and causes the workstation to
hang. This patch ensures that Xtrieve properly tracks current line and
column positions.
NOTE: If a group contains any fields, do not define group control fields
with a line position of +0. In most cases, this operation does not
produce the intended printed results. Instead, define the group with
a line position of +1, which places each occurence of the fields in
the group on a new line.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: EMPTY FIELD, NOTE, SDF, TRANSLATE
Problem Fixed by This Patch:
When translating a view including a NOTE or LVAR field that contains no data
into SDF format, Xtrieve produces a field value of (HEX) 0xF9 in double
quotation marks. This patch ensures that Xtrieve translates the value as ""
with no data included between the quotes.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: 221, USER-DEFINED FIELD
Problem Fixed by This Patch:
Xtrieve returns a Status Code 221 (Invalid Syntax for Expression or
Restriction) when building an expression for a user-defined field. This
patch ensures that Xtrieve always zero-terminates a user-defined field
expression before sending that expression to NetWare SQL for processing.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: LOADING WITH /? OR /H, XTRTMP_*.*, ZERO BYTES
Problem Fixed by This Patch:
When you load Xtrieve with the /?, or /h parameters, it leaves XTRTMP_M.*
and XTRTMP_L.* files with zero bytes in the XTRTMP directory. This patch
ensures that Xtrieve always removes XTRTMP_*.* files when it terminates.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: F1, HEAP SPACE, HELP
Problem Fixed by This Patch:
Xtrieve occasionally returns the message "Out of local heap space" when you
press F1 for help. This patch ensures that Xtrieve always reserves enough
space in memory for the help text.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: EXTRA 0, FLOAT, MASK
Problem Fixed by This Patch:
Xtrieve adds an extra zero following the decimal point to float values when
the display mask for those values contains the special () literals. This
patch ensures that these special literals do not affect the number of
digits following the decimal point.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: EXTRA BLANK PAGE, PRINT DEFINITION
Problem Fixed by This Patch:
When you print a definition (view, report, or dictionary table), Xtrieve
prints an extra blank page before printing the actual definition. This
patch ensures that the first printed page is the first page of the
definition.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: CONDITIONAL, USER-DEFINED FIELD
Problem Fixed by This Patch:
Xtrieve does not properly define a user-defined field if its definition is
based on a conditional statement and other user-defined fields. The problem
occurs when you include in the definition a condition that compares two
user-defined fields. This patch ensures that Xtrieve includes the correct
fields in a conditional user-defined field and correctly defines the entire
field.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: DEFINITION, PRINT, VIEW
Problem Fixed by This Patch:
When printing a large view definition, such as one with many joined files,
Xtrieve displays the following error message: "Error writing output." This
patch ensures that Xtrieve allocates a buffer large enough to handle
multiple joined file views so that you can print the definition of such a
view.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: DICTIONARY, INDEX, PRINT, SHOW
Problem Fixed by This Patch:
If you drop an index from a table definition and do not renumber the
remaining indexes, Xtrieve does not display the definitions for indexes with
a number higher than the one that was dropped. This patch ensures that
Xtrieve correctly finds all index definitions when showing or printing a
table definition.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: COMPLETE, RESTRICT, VARIABLE FIELD
Problem Fixed by This Patch:
In some cases, you cannot complete a restriction when that restriction
includes a variable length field because Xtrieve occasionally overwrites
memory in this situation. This patch ensures that no memory overwrite
occurs, enabling you to complete the restriction.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: 213, OWNER NAME, VIEW
Problem Fixed by This Patch:
Xtrieve displays Status Code 213 (Read Access) when the XTROWNER variable
does not contain the owner name(s) required to recall a view definition.
This patch ensures that Xtrieve requests the owner names when recalling a
view just as it does when opening a table for a view. The only difference
is that Xtrieve asks for an owner name each time after you press Enter until
you press ESC, or until you press Enter if you have not typed a name at the
prompt.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: /D PARAMETER, /K PARAMETER, COMMAND FILE, KEYBOARD FILE,
LOADING XTRIEVE
Problem Fixed by This Patch:
Xtrieve does not load successfully when you specify a keyboard input file
along with the /D parameter. This patch ensures that you can load Xtrieve
when you specify the /D parameter and a keyboard input file, provided that
you also specify either the /K parameter or a command file.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: DATE FIELD, DIF FILE, LOTUS 123
Problem Fixed by This Patch:
When Xtrieve translates a date field into a DIF file format and you then
load the DIF file into Lotus 123, the date value appears as ******. (This
problem occurs only when Xtrieve is loaded and you are using XQLP 2.x.) This
patch ensures that Xtrieve correctly translates the date values to the DIF
file format.
* * * * * * * * *
Product/Platform: OS/2 - XTRIEVE.EXE, v4.11
Search Strings: 227, USER-DEFINED FIELD
Problem Fixed by This Patch:
When the menu for a user-defined field definition is full and cannot hold
any additional entries, Xtrieve displays Status Code 227 (Operand Must Be a
Dictionary Field) when completing the definition. This patch ensures that
Xtrieve correctly tracks the table name for a field when the menu
is full and then builds the definition correctly.
* * * * * * * * *
Product/Platform: OS/2 - MAKE_XTA.EXE, v4.11
Search Strings: COMMAND FILE NOT REPLAYABLE, REPORT LAYOUT DEFINITION, XCFP
Problem Fixed by This Patch:
When MAKE_XTA extracts a report layout definition and XCFP converts that
.XTA file to an .XTC file, Xtrieve returns the error message "Command file
contains keystroke which is not replayable," and the command file does not
complete. This patch modifies the way in which MAKE_XTA builds .XTA files
for report layouts so that the command file contains valid keystrokes and
builds the correct report.
* * * * * * * * *
Product/Platform: OS/2 - MAKE_XTA.EXE, v4.11
Search Strings: APPEND, BRACKET COMMAND, CONCATENATE, USER-DEFINED STRING
FIELD
Problem Fixed by This Patch:
When converting a user-defined field into an .XTA file, MAKE_XTA adds a
.BRACKET. command when it attempts to append one string to another string or
to concatenate two strings. This patch ensures that MAKE_XTA does not
insert a .BRACKET. command when converting a user-defined string field.
* * * * * * * * *
Product/Platform: OS/2 - MAKE_XTA.EXE, v4.11
Search Strings: FIELD HEADINGS AND OFFSETS, VIEWS
Problem Fixed by This Patch:
When MAKE_XTA converts a view, it occasionally uses the field names, rather
than the user-specified headings, for the fields in the view. Also,
MAKE_XTA does not insert the correct field offset. This patch ensures that
MNAKE_XTA employs the user-specified field heading for all fields and
inserts the correct field offset.
* * * * * * * * *
Product/Platform: OS/2 - MAKE_XTA.EXE, v4.11
Search Strings: MULTIPLE FIELD NAMES, TABLE NAMES, VIEWS
Problem Fixed by This Patch:
When MAKE_XTA converts a view, it does not select the correct occurrence of
a field when the field name appears more than once in the view. (This
occurs because MAKE_XTA does not accurately determining the correct table
name for the field.) This patch ensures that when you are rebuilding a view
definition, MAKE_XTA determines the correct table name whenever you select a
field name from a menu.
* * * * * * * * *
Product/Platform: OS/2 - MAKE_XTA.EXE, v4.11
Search Strings: COMMAND FILE, ESC COMMANDS, FOOTER, HEADER
Problem Fixed by This Patch:
When a report contains a header or footer, MAKE_XTA does not place the
correct number of .ESC. commands in the command file. As a result, the
command file does not replay correctly in Xtrieve. This patch ensures that
MAKE_XTA places the correct number of .ESC. commands in the command file
for report headers and footers.
* * * * * * * * *
Product/Platform: OS/2 - XCFP.EXE, v4.11
Search Strings: COMMAND FILE, FMENU COMMAND, XTA TO XTC CONVERSION
Problem Fixed by This Patch:
When XCFP converts an .XTA file containing an .FMENU. command to an .XTC
file, XCFP does not place the commands in the command file. This patch
ensures that XCFP correctly interprets an .FMENU. command and includes it
correctly in the .XTC file.
* * * * * * * * *
================================================================================
Documentation Updates
=====================
NOTE: The documentation updates that follow are supplement any documentation
updates noted in the Readme file of the original product. Note that
only the December 1992 patch release included such updates.
December 1992 Updates
---------------------
Note the following change to the "Xtrieve PLUS User's Manual:"
- Page A-49
Add the following status codes:
349 The Specified Data Value Is Too Large for the Field Definition
The data value you specified is larger than the maximum length
defined for the field.
350 Security Has Not Been Enabled on This Dictionary
You attempted an operation that can be done only when security is
enabled. Database security is not enabled at this time. To perform
the operation successfully, enable security on that database.
351 A Transaction Has Not Yet Been Started
You attempted to perform a COMMIT or ROLLBACK operation without being
inside a transaction. You must start a transaction before you can
perform a COMMIT or ROLLBACK operation. To start a transaction,
issue a START TRANSACTION operation.
352 Record Count Must Be Greater Than Zero
NetWare SQL received a record count value for the xFetch call that is
not more than zero. The record count for an xFetch call must be at
least 1.
================================================================================
Novell, Inc. has attempted to supply trademark information about company
names, products, and services mentioned in this file. The following list of
trademarks was derived from various sources.
NetWare, Novell, Btrieve, and XQL are registered trademarks of Novell, Inc.
NetWare Btrieve, NetWare Loadable Module, NetWare SQL, NLM, and Xtrieve PLUS
are trademarks of Novell, Inc.
NetWire is a registered service mark of Novell, Inc.
1-2-3 and Lotus are registered trademarks of Lotus Development Corporation.
CompuServe is a registered trademark of CompuServe, Incorporated.
OS/2 is a registered trademark of International Business Machines
Corporation.
** End of XTROS2.TXT **